home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
CD ROM Paradise Collection 4
/
CD ROM Paradise Collection 4 1995 Nov.iso
/
music
/
audiovdd.zip
/
README.DOS
< prev
next >
Wrap
Text File
|
1992-11-24
|
2KB
|
47 lines
Instructions for installing the DOS Virtual Audio driver:
Prerequisites:
1) You must have a 386 or 386SX or above PC
2) You must be using DOS 5.0
3) Memory managers such as EMM386 or QEMM386 must not be installed.
HIMEM is ok, and should be used to load DOS high (refer to your
DOS documentation).
The VDD will attempt to map the sounds requested by the application to
the nearest M-ACPA sound. In most cases this is quite acceptable, but
in any case it will sound different.
/****************************************************************************/
Install Instructions
/****************************************************************************/
1) Copy the IBMMPC.DSP file to the root of the C: drive
2) Copy the following drivers to a directory on your hard drive:
SVAUDIO.EXE
ACPAD2.SYS
Ensure that the directory is included in your PATH statement.
3) Update your C:\CONFIG.SYS to include:
device=ACPAD2.SYS 1
4) Reboot your system.
5) Prior to running any audio programs, load the driver by entering:
SVAUDIO
The driver will remain installed until the next boot.
/****************************************************************************/
The TSR requires approximately 28K of memory. Typically, on a machine
running DOS 5.0, approximately 470K of memory is available. Optionally,
loading DOS in high memory(with HIMEM) leaves approximately 520K of memory
available. Note that this precludes running a number of applications
which require memory in excess of these figures.
Many applications operate in 'direct mode' whereby data is sent
directly to the audio card DSP through IN/OUT instructions. This mode
is not supported and such applications will not work. Also, some
applications use the audio card interface to control timing. These also
will not work at this time.
A final caveat: the SVAUDIO TSR uses the 386 protect mode logic to
monitor for selected audio-related events. It is not compatible with
existing extenders or, in general, with any other software that uses
protect mode. Error handling is not very robust at this time. Be prepared
to reboot.